I ran into this same problem with 'json'. I have to prepare the request either way to send it, so it makes sense for the OpenAPI Request object to be created from that.

I ran into problems trying to support requests with multipart/form-data. Nothing else worked, so I tried using this version. It does not solve the problem:

openapi_core.schema.media_types.exceptions.InvalidContentType: Content for following mimetype not found: multipart/form-data; boundary=6c20c84fd95c1d9ac73bcc7ed47fa1c0

edit: or does it hmmmm

I was using this code successfully, but it stopped working after updated openapi-core 0.13.6 to 0.13.7 with urlencoded bodies. It seems the urlencoded string gets validated rather than the decoded dictionary of values. I suspect it never worked but didn't signal an error because of abfd0c6.

Edit: I had to add a deserializer:

openapi_request_validator = RequestValidator(
    openapi_spec,
    custom_media_type_deserializers={
        'application/x-www-form-urlencoded': lambda v: v if isinstance(v, dict) else dict(urllib.parse.parse_qsl(v)),
    },
)

Codecov Report

Merging #271 (ff4a6c8) into master (6a222b9) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #271      +/-   ##
==========================================
+ Coverage   96.75%   96.77%   +0.01%     
==========================================
  Files         122      122              
  Lines        2436     2448      +12     
==========================================
+ Hits         2357     2369      +12     
  Misses         79       79              

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6a222b9...ff4a6c8. Read the comment docs.

@eyadgaran thank you for the contribution.